ci(changelog): 👷 Use explicit prev_tag for draft release changelog #27
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add previous stable tag detection to draft-release workflow so changelog-action generates correct diff range even when the current tag is a pre-release (e.g. beta-xxx). Aligns with the same approach used in changelog.yml. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
draft-release.ymlusing the same logic aschangelog.ymlfromTag/toTaginstead oftagin changelog-action to explicitly specify the diff rangefetch-depth: 0on checkout to access all tagsThis ensures the draft release changelog generates correctly even when the current tag is a pre-release name (e.g.
beta-xxx), by always comparing against the last stableX.Y.Ztag.Test Plan
beta-1.0.0) and verify draft release is created with correct changelog1.0.0) and verify changelog still works as expectedprev_tagoutput is logged correctly in workflow run🤖 Generated with Claude Code